Model-driven implementation of services on a software-defined network

ABSTRACT

A method includes receiving, at a model and optimization framework, a request, rendered in a first format, for a service to be implemented on a subset of a software-defined network. The request includes at least one constraint affecting implementation of the service. The method includes producing an optimized solution, rendered in a second format, for implementing the service based on the at least one constraint. The method includes translating the optimized solution to the first format and providing instructions for a cloud manager to implement the service consistent with the translated optimized solution.

CROSS-REFERENCE TO RELATED APPLICATIONS

The instant application is a divisional application of, and claimspriority to, U.S. patent application Ser. No. 15/487,621, filed Apr. 14,2017. U.S. patent application Ser. No. 15/487,621 is incorporated hereinby reference in its entirety.

BACKGROUND

In traditional environments, optimization of assets, services, and otherelements may be done on a case-by-case basis. Such an approach mayproduce specialized solutions for each problem, that are difficult togeneralize and maintain. Thus, even small changes in the problemdefinition may require a large amount of effort to modify the solution,increasing the cost and time of development and maintenance of suchsolutions.

SUMMARY

The disclosed systems, methods, and apparatuses allow for solvingoptimization problems using a generic framework adaptable to providecustom solutions for a variety of problems related to implementation ofa service on a software-defined network (SDN).

In an aspect, this disclosure is directed to a method. The method mayinclude receiving, at a model and optimization framework, a request fora service to be performed on a software-defined network and receiving apolicy affecting the service from a policy engine. The method mayinclude producing a mathematical model based on the service, the policy,and a constraint and producing a translation key based on themathematical model. The method may include analyzing the mathematicalmodel using an optimization engine to generate an optimized solution forexecuting the service. The method may also include translating theoptimized solution based on the translation key and providing thetranslated optimized solution via the model and optimization framework.The translated optimized solution may provide instructions for a cloudmanager to execute the service consistent with the optimized solution.

According to another aspect, this disclosure is directed to a system.The system may include a model and optimization frameworkcommunicatively coupled to a software-defined network. The model andoptimization framework may include a policy engine and an optimizationengine communicatively coupled to the policy engine. The system mayinclude a processor communicatively coupled to the model andoptimization framework. The system may include memory storinginstructions that cause the processor to effectuate operations. Theoperations may include receiving, at the model and optimizationframework, a request for a service to be performed on a subset of thesoftware-defined network. The operations may include receiving a policyaffecting the service from the policy engine. The operations may includeproducing a mathematical model based on the service, the policy, and aconstraint. The operations may include producing a translation key basedon the mathematical model. The operations may include analyzing themathematical model using the optimization engine to generate anoptimized solution for executing the service. The operations may includetranslating the optimized solution based on the translation key andproviding the translated optimized solution via the model andoptimization framework. The translated optimized solution providesimplementation instructions for a cloud manager to execute the serviceconsistent with the optimized solution.

In another aspect, this disclosure is directed to a non-transitorycomputer-readable storage medium storing instructions that cause aprocessor executing the instructions to effectuate operations. Theoperations may include receiving, at a model and optimization framework,a request for a service to be performed on a subset of asoftware-defined network. The operations may include receiving a policyaffecting the service from a policy engine. The operations may includeproducing a mathematical model based on the service, the policy, and aconstraint and producing a translation key based on the mathematicalmodel. The operations may include analyzing the mathematical model usingan optimization engine to generate an optimized solution for executingthe service and translating the optimized solution based on thetranslation key. The operations may include providing the translatedoptimized solution via the model and optimization framework. Thetranslated optimized solution may provide implementation instructionsfor a cloud manager to execute the service consistent with the optimizedsolution.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein service implementation systems and methods aredescribed more fully herein with reference to the accompanying drawings,in which example embodiments are shown. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide an understanding of the various embodiments. However,the instant disclosure may be embodied in many different forms andshould not be construed as limited to the example embodiments set forthherein. Where convenient, like numbers refer to like elements.

FIG. 1 is a schematic of a system for implementing services on an SDN.

FIG. 2 is a flowchart of an exemplary method for implementing a serviceon an SDN.

FIG. 3 is a schematic of an exemplary device that may be a component ofthe system of FIG. 1.

FIG. 4 illustrates a functional block diagram depicting an exemplarynetwork architecture.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500.

FIG. 6 is a diagram of an exemplary telecommunications system in whichthe disclosed systems or methods may be implemented.

FIG. 7 is an example system diagram of a radio access network and a corenetwork upon which an application may be deployed using the disclosedsystems or methods.

FIG. 8 illustrates an architecture of a typical GPRS network 900 asdescribed herein.

FIG. 9 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system.

DETAILED DESCRIPTION

FIG. 1 is a schematic of a system 100 for facilitating implementation ofservices on an SDN 110. SDN 110 may be a network on which virtualfunctions operate, a cloud-like environment, or any other type ofsoftware-defined network or environment. For example, in SDN 110, one ormore services, assets, or other elements may be model-driven. SDN 110may be an agile environment. For example, constraints on such networkassets may be dynamically changed. Thus, model-driven solutions that aregeneral and can be adapted in a flexible manner may be advantageous forserving SDN 110.

System 100 may include a model and optimization framework 112 that mayimplement services or other changes on SDN 110. Model and optimizationframework 112 may consider service requests, policies, and data fromadditional support systems in a model-driven manner to implementservices on SDN 110. Model and optimization framework 112 may be genericenough to implement a wide variety of solutions on SDN 110 throughautomatic model creation and optimization.

In operating, maintaining, or building SDN 110, one or more services maybe implemented on SDN 110. There may be multiple requests for servicesto the same SDN 110, and the implementation of that service—for example,the solution for implementing a particular requested service—may takemultiple forms. Thus, determining when and how to implement services onSDN 110 may become a complex, multi-factor decision-making process. Asthe need for decreasing down time of SDN 110 and decreasing the leadtime for implementing services on SDN 110. Thus, a generic automation ofthe service request and implementation process may be necessary incertain circumstances to satisfy demand on SDN 110.

Operation of model and optimization framework 112 may be understood withreference to flowchart 200 of FIG. 2. At step 202, model andoptimization framework 112 may receive a request for a service to beimplemented on at least a subset of SDN 110. Model and optimizationframework 112 may include a request input/output 114 for receiving theservice request. The service request may be in a particular format, suchas a business model language. The service request may indicate one ormore requirements, constraints, or optimization parameters forimplementing the service on SDN 110. For example, the service requestmay identify the entity or entities that may be affected byimplementation of the service. As another example, implementing aservice or making a change to SDN 110 may be performed in accordancewith a schedule. The service request may include one or more constraintson the schedule, such as allowed or forbidden periods in which changesmay be performed. Another example of a schedule-related constraint maybe an order in which certain changes may need to be performed.

At step 204, method 200 may include receiving a policy affecting theservice. This may include a policy affecting a type of the service, apolicy affecting a constraint on the service or a policy affectingimplementation of the service, or a policy affecting any other aspect ofthe service. Policies may be stored by or retrieved by a policy engine116 of model and optimization framework. The policies may be stored in apolicy platform (not shown). Policy engine 116 may contain or maycommunicate with such a policy platform. Policies may includeprioritizing certain constraints over another. For example, if nosolution is found that satisfies all of the constraints, a policy maydictate which constraints can be disregarded to find a solution.Policies may include optimization parameters, such as a maximumoptimization time, alternative solutions, or other business constraints.

At this point, the service request, including applicable constraints,and policies may be known by model and optimization framework 112.Additional data or information may be retrieved to formulate anoptimized solution for implementing the service. For example,information about SDN 110 may be obtained. This information may includethe current utilization of resources in SDN 110, the kind of equipmentused or available in SDN 110, or the like. Additional limitations may beadded to the service at this time. For example, additional constraintsmay be added based on the information about SDN 110 or based on thepolices from policy engine 116.

At step 206, a mathematical modeler 118 of the model and optimizationframework 112 may produce a mathematical model based on this informationrelated to the service. For example, the mathematical model may be basedon the service, the policy, and a constraint. Optionally, in addition tothe mathematical model, additional data may be generated at this time.The model may be in any format sufficient for entering into anoptimization engine. For example, the format of the mathematical modelmay include a MathProg, CMPL, AMPL, or OPL format, or the like.

At step 208, mathematical modeler 118 may optionally produce atranslation key based on the mathematical model. For example, thetranslation key may later be used to translate the solution into thesame format or business model language as the service request.

At step 210, method 200 may include an optimization engine 120 of modeland optimization framework 112 performing an optimization by analyzingthe mathematical model and, optionally additional data. For example,this additional data may include auxiliary mathematical models, whichmay be generated by or retrieved from mathematical modeler 118.Optimization engine 120 may be one of a plurality of optimizationengines 120. Thus, step 210 may optionally include selectingoptimization engine 120 from the plurality of optimization engines 120.This selection of the optimization engine may be based on themathematical model, auxiliary mathematical model, or other information.For example, the plurality of optimization engines may include a linearor nonlinear mixed integer programming engine, a constraint programmingengine, an evolutionary computation engine, a swarm optimization engine,or a metaheuristics engine. Optimization engine 120 that performs theoptimization on the mathematical model may be one or more of these typesof engines. Multiple optimization engines 120 may be used in parallel,sequentially, or in combination to optimize the mathematical model. Theoutput of the optimization engine 120 may be the optimized solutionresponsive to the request. For example, the optimized solution may befor executing the service indicate by the request. The optimizedsolution may be in a language or format similar to or based on thelanguage of the mathematical model.

Thus, at step 212, a translator 122 of model and optimization framework112 may translate the optimized solution into a translated optimizedsolution. The translated optimized solution may be in a format or abusiness model language that is similar to or the same as the businessmodel language or format as the request.

At step 214, model and optimization framework 112 may provide thetranslated optimized solution. This may include transmitting thetranslated optimized solution via a cloud manager 124. This may includepublishing the translated optimized solution via the model andoptimization framework 124, such as for review by a user. For example,the translated optimized solution may be published or made available viarequest input/output 114, either through cloud manager 124 or directlyfrom translator 122. The translated optimized solution may provideimplementation instructions for cloud manager 124 to execute the serviceconsistent with the optimized solution.

Optionally, method 200 may include actually implementing the solution onSDN 110. In this manner, model and optimization framework 110 may be ageneric portal for receiving requests and changing SDN 110 in accordingwith those requests.

FIG. 3 is a block diagram of network device 300 that may be connected toor comprise a component of system 100. For example, network device 300may implement one or more portions of method 200. Network device 300 maycomprise hardware or a combination of hardware and software. Thefunctionality to facilitate telecommunications via a telecommunicationsnetwork may reside in one or combination of network devices 300. Networkdevice 300 depicted in FIG. 3 may represent or perform functionality ofan appropriate network device 300, or combination of network devices300, such as, for example, a component or various components of acellular broadcast system wireless network, a processor, a server, agateway, a node, a mobile switching center (MSC), a short messageservice center (SMSC), an ALFS, a gateway mobile location center (GMLC),a radio access network (RAN), a serving mobile location center (SMLC),or the like, or any appropriate combination thereof. It is emphasizedthat the block diagram depicted in FIG. 3 is exemplary and not intendedto imply a limitation to a specific implementation or configuration.Thus, network device 300 may be implemented in a single device ormultiple devices (e.g., single server or multiple servers, singlegateway or multiple gateways, single controller or multiplecontrollers). Multiple network entities may be distributed or centrallylocated. Multiple network entities may communicate wirelessly, via hardwire, or any appropriate combination thereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example, input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be at least partiallyimplemented as using virtualized functions. Network architecture 400disclosed herein is referred to as a modified LTE-EPS architecture 400to distinguish it from a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. LTE-EPS network architecture400 may include an access network 402, a core network 404, e.g., an EPCor Common BackBone (CBB) and one or more external networks 406,sometimes referred to as PDN or peer entities. Different externalnetworks 406 can be distinguished from each other by a respectivenetwork identifier, e.g., a label according to DNS naming conventionsdescribing an access point to the PDN. Such labels can be referred to asAccess Point Names (APN). External networks 406 can include one or moretrusted and non-trusted external networks such as an internet protocol(IP) network 408, an IP multimedia subsystem (IMS) network 410, andother networks 412, such as a service network, a corporate network, orthe like. In an aspect, access network 402, core network 404, orexternal network 405 may include or communicate with system 100.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity, andtriggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an Sl-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., Slsignaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes, e.g., by one or moreof tunnel endpoint identifiers, an IP address and a user datagramprotocol port number. Within a particular tunnel connection, payloads,e.g., packet data, which may or may not include protocol relatedinformation, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. SGW 420can serve a relay function, by relaying packets between two tunnelendpoints 416 a, 426. In other scenarios, direct tunneling solution 458can forward user data packets between eNB 416 a and PGW 426, by way ofthe S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual basis. If user data packets of one bearer, say a bearerassociated with a VoIP service of UE 414, then the forwarding of allpackets of that bearer are handled in a similar manner. Continuing withthis example, the same UE 414 can have another bearer associated with itthrough the same eNB 416 a. This other bearer, for example, can beassociated with a relatively low rate data session forwarding user datapackets through core network 404 simultaneously with the first bearer.Likewise, the user data packets of the other bearer are also handled ina similar manner, without necessarily following a forwarding path orsolution of the first bearer. Thus, one of the bearers may be forwardedthrough direct tunnel 458; whereas, another one of the bearers may beforwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise a mobile device, network device 300, or the like, or anycombination thereof. By way of example, WTRUs 602 may be configured totransmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. WTRUs 602 may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, one or more WTRUs 602 may be configured tocommunicate with base station 616, which may employ a cellular-basedradio technology, and with base station 616, which may employ an IEEE802 radio technology.

FIG. 7 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 8 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 8. Inan example, device 910 comprises a communications device (e.g., device120, network device 300, or the like, or any combination thereof). Radioaccess network 904 comprises a plurality of BSSs such as BSS 912, whichincludes a BTS 914 and a BSC 916. Core network 906 may include a host ofvarious network elements. As illustrated in FIG. 8, core network 906 maycomprise MSC 918, service control point (SCP) 920, gateway MSC (GMSC)922, SGSN 924, home location register (HLR) 926, authentication center(AuC) 928, domain name system (DNS) server 930, and GGSN 932.Interconnect network 908 may also comprise a host of various networks orother network elements. As illustrated in FIG. 8, interconnect network908 comprises a PSTN 934, an FES/Internet 936, a firewall 1038, or acorporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 8, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 9 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 9, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, device 120, vehicle 103, network device 300,the like, or any combination thereof may serve as MS 1002. MS 1002 maybe one of, but not limited to, a cellular telephone, a cellulartelephone in combination with another electronic device or any otherwireless mobile communication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically, MS 1002 may communicate with any or all of BSS 1004, RNS1012, or E-UTRAN 1018. In an illustrative system, each of BSS 1004, RNS1012, and E-UTRAN 1018 may provide MS 1002 with access to core network1010. Core network 1010 may include of a series of devices that routedata and communications between end users. Core network 1010 may providenetwork service functions to users in the circuit switched (CS) domainor the packet switched (PS) domain. The CS domain refers to connectionsin which dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location data such as, butnot limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation data.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location data. HSS 1042 may also provide call or sessionestablishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location data to the VLR for thearea. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

While examples of a telecommunications system in which virtual functionscan be deployed have been described in connection with various computingdevices/processors, the underlying concepts may be applied to anycomputing device, processor, or system capable of facilitating atelecommunications system. The various techniques described herein maybe implemented in connection with hardware or software or, whereappropriate, with a combination of both. Thus, the methods and devicesmay take the form of program code (i.e., instructions) embodied inconcrete, tangible, storage media having a concrete, tangible, physicalstructure. Examples of tangible storage media include floppy diskettes,CD-ROMs, DVDs, hard drives, or any other tangible machine-readablestorage medium (computer-readable storage medium). Thus, acomputer-readable storage medium is not a signal. A computer-readablestorage medium is not a transient signal. Further, a computer-readablestorage medium is not a propagating signal. A computer-readable storagemedium as described herein is an article of manufacture. When theprogram code is loaded into and executed by a machine, such as acomputer, the machine becomes a device for telecommunications. In thecase of program code execution on programmable computers, the computingdevice will generally include a processor, a storage medium readable bythe processor (including volatile or nonvolatile memory or storageelements), at least one input device, and at least one output device.The program(s) can be implemented in assembly or machine language, ifdesired. The language can be a compiled or interpreted language, and maybe combined with hardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed:
 1. A method comprising: receiving, at a model andoptimization framework, a request, rendered in a first format, for aservice to be implemented on a software-defined network, wherein therequest comprises at least one constraint affecting implementation ofthe service; producing an optimized solution, rendered in a secondformat, for implementing the service based on the at least oneconstraint; translating the optimized solution to the first format; andproviding instructions for a cloud manager to implement the serviceconsistent with the translated optimized solution.
 2. The method ofclaim 1, further comprising obtaining an auxiliary mathematical model,wherein the optimized solution is further based on the auxiliarymathematical model.
 3. The method of claim 2, further comprisingselecting the optimization engine from a plurality of engines based onat least one auxiliary mathematical model.
 4. The method of claim 3,wherein the plurality of engines comprises at least one of a mixedinteger programming engine, a constraint programming engine, anevolutionary computation engine, a swarm optimization engine, or ametaheuristics engine.
 5. The method of claim 1, further comprising:designing a mathematical model based on the request, the mathematicalmodel rendered in the second format, wherein producing the optimizedsolution is based on the mathematical model.
 6. The method of claim 1,further comprising implementing the service based on the translatedoptimized solution.
 7. The method of claim 1, wherein the constraintcomprises a schedule constraint that restricts timing of implementingthe optimized solution on the software-defined network.
 8. A systemcomprising: a model and optimization framework communicatively coupledto a software-defined network, the model and optimization frameworkcomprising a policy engine and an optimization engine communicativelycoupled to the policy engine; a processor communicatively coupled to themodel and optimization framework; and memory storing instructions thatcause the processor to effectuate operations, the operations comprising:receiving a request, rendered in a first format, for a service to beimplemented on a subset of the software-defined network, wherein therequest comprises at least one constraint affecting implementation ofthe service; producing an optimized solution using the optimizationengine, the optimized solution for implementing the service based on theat least one constraint, the optimized solution rendered in a secondformat; translating the optimized solution to the first format; andproviding instructions for a cloud manager to implement the serviceconsistent with the translated optimized solution.
 9. The system ofclaim 8, wherein the first format is based on a business model languageand translating the optimized solution into the first format comprisestranslating the optimized solution into the business model language. 10.The system of claim 8, the operations further comprising producing atranslation key based on the request, wherein translating the optimizedsolution is further based on the translation key.
 11. The system ofclaim 8, the operations further comprising facilitating implementationof the service based on the translated optimized solution.
 12. Thesystem of claim 8, the operations further comprising obtaining anauxiliary mathematical model, wherein the optimized solution is furtherbased on the auxiliary mathematical model.
 13. The system of claim 12,the operations further comprising selecting the optimization engine froma plurality of engines based on the auxiliary mathematical model. 14.The system of claim 13, wherein the plurality of engines comprises atleast one of a mixed integer programming engine, a constraintprogramming engine, an evolutionary computation engine, a swarmoptimization engine, or a metaheuristics engine.
 15. A non-transitorycomputer-readable storage medium storing instructions that cause aprocessor executing the instructions to effectuate operations, theoperations comprising: receiving, at a model and optimization framework,a request, rendered in a first format, for a service to be implementedon a subset of a software-defined network, wherein the request comprisesat least one constraint affecting implementation of the service;producing an optimized solution, rendered in a second format, forimplementing the service based on the at least one constraint;translating the optimized solution to the first format; and providinginstructions for a cloud manager to implement the service consistentwith the translated optimized solution.
 16. The non-transitorycomputer-readable storage medium of claim 15, wherein the first formatis in a business language and translating the optimized solutioncomprises translating the optimized solution into the business language.17. The non-transitory computer-readable storage medium of claim 15,wherein the constraint is a schedule-related constraint.
 18. Thenon-transitory computer-readable storage medium of claim 15, theoperations further comprising: obtaining an auxiliary mathematicalmodel; and selecting the optimization engine from a plurality of enginesbased on the auxiliary mathematical model.
 19. The non-transitorycomputer-readable storage medium of claim 18, wherein the plurality ofengines comprises at least one of a mixed integer programming engine, aconstraint programming engine, an evolutionary computation engine, aswarm optimization engine, or a metaheuristics engine.
 20. Thenon-transitory computer-readable storage medium of claim 15, wherein theat least one constraint comprises a first constraint and a secondconstraint and wherein producing the optimized solution comprisesprioritizing the constraint over a second constraint if no solutionexists that satisfies both the constraint and the second constraint.